<!-- title Contributing -->

<div class="left-column">

<h2 id="developer_info">Resources for Developers</h2>

<h3 id="issuetracker"><a href="http://code.google.com/p/go/issues">Issue Tracker</a></h3>
<p>Having an issue with Go? Check the tracker to see if it's a known issue.</p>
<p>If your issue is not listed, please file a <a
href="http://code.google.com/p/go/issues/entry">bug report</a>.</p>

<h3 id="build_status"><a href="http://godashboard.appspot.com/">Build Status</a></h3>
<p>View the status of Go builds across the supported operating
systems and architectures.</p>

<h3 id="contibute"><a href="contribute.html">Contribution Guidelines</a></h3>
<p>So, you want to contribute code to the Go project? That's great!</p>
<p>The first step is to read these contributions guidelines for information on 
design, testing, and our code review process.</p>

</div>

<div class="right-column">

<h2 id="">The Go Project</h2>

<h3 id="roadmap"><a href="devel/roadmap.html">Roadmap</a></h3>
<p>Features and ideas being developed or discussed by the Go team.</p>

<h3 id="release"><a href="devel/release.html">Release History</a></h3>
<p>A summarization of the changes between tagged releases of Go.</p>

<h3 id="golang-dev"><a href="http://groups.google.com/group/golang-dev">Developer Mailing List</a></h3>
<p>The <a href="http://groups.google.com/group/golang-dev">golang-dev</a>
mailing list is for discussing and reviewing code for the Go project.</p>
<p>For general discussion of Go programming, see <a
href="http://groups.google.com/group/golang-nuts">golang-nuts</a>.</p>

<h3 id="golang-checkins"><a href="http://groups.google.com/group/golang-checkins">Checkins Mailing List</a></h3>
<p>A mailing list that receives a message summarizing each checkin to the Go repository.</p>

</div>

<div class="end-columns"></div>

